Using STL synchronisation primitives like std::mutex should be thread-affine. If a user calls std::mutex::lock, then yield, then resume, then std::mutex::unlock, it's a bug because the fiber could migrate to another thread. But in my experience, it's quite hard to hit that bug in CI. To make it much simpler, I suggest we always add the fiber to the global ready queue under TSan.